Information recorder, recording method, and recording media

ABSTRACT

There are described a data recording system, a data recording method, and a recording medium, all of which are directed to enabling easy editing of AV data without involvement of duplication of the AV data, as well as to eliminating a necessity for an additional data recording region. In the recording system, at the time of recording of primary data, there is prepared an original file which stores link data formed by arranging in sequence address data for reproduction purposes stored in a recording region on a recording medium. Further, through editing of the original file, there is prepared a virtual file which stores link data formed by arranging in sequence address data for reproduction purposes stored in the recording region on the recording medium. The data are reproduced according to these files.

FIELD OF THE INVENTION

The present invention relates to a data recording system, a datarecording method, and a recording medium.

BACKGROUND ART

In a conventional video system, recorded audio-visual (AV) data areedited through the following processes. The video system employs areproduction system for reproducing the recorded AV data and a recordingsystem for recording the AV data reproduced by the reproduction system.Desired portions of the AV data are recorded on the recording systemwhile the AV data are reproduced by the reproduction system. Forexample, when an attempt is made to create a digest of certain AV data,the AV data are edited through the processes mentioned above. Forexample, as shown in FIG. 21, when an attempt is made to create a newvideo file from a portion of a first video file including first videodata and a portion of a second video file including second video data,there is a necessity for producing a duplicate of the correspondingportion of the first video file and a duplicate of the correspondingportion of the second video file.

According to the standards for an existing mini disk (MD), audio dataare not recorded on a track in adjacent locations but are discretelyrecorded on the track in recording units, each comprising apredetermined amount of data. In order to reproduce a string of datafrom the discrete data sets, there is provided a management table foruse in linking the discrete data sets together. The reproduction systemaccesses the discrete data in the sequence written in the managementtable, to thereby enable reproduction of sequential sound.

In the above-described conventional video system, editing of recorded AVdata involves use of two VCRs. Further, since AV data must be duplicatedwhile editing, an additional recording area for recording the duplicateof the AV data is required.

According to the existing MD standards, each of the linked data setsassumes a predetermined amount of recorded data, and only a singlemanagement table is assigned to a mini disk. If other data areoverwritten on a disk on which data have already been recorded, theexisting management table must be rewritten. Thus, only single link dataare available. For these reasons, in order to edit data, the data mustbe duplicated as in the conventional video system. A significant problemis not encountered in a case where there is little necessity for editingdata, such as the case of an MD. In contrast, in the case of AV data, itis expected that there is an increasing user demand for creating adigest of certain AV data.

Further, the conventional file system can share a file but cannot sharea portion of a file.

The present invention is directed to an system and method for enablingeasy editing of AV data. Particularly, the object of the presentinvention is to provide a data recording system, a data recordingmethod, and a recording medium, wherein AV data can be readily editedwithout involvement of duplication of the AV data and without anecessity for an addition data recording area.

SUMMARY OF THE INVENTION

The present invention has been conceived to solve the foregoing problem.According to a first aspect of the present invention, there is provideda data recording system for recording primary data, comprising:

-   -   a recording section for recording primary data; and    -   a control section which generates an original file at the time        of recording of the primary data, and a virtual file through        editing of the original file, wherein the original file stores        link data which are formed by arranging in sequence address data        for reproduction purposes stored in a recording region on a        recording medium, and the virtual file stores link data which        are formed by arranging in sequence address data for        reproduction purposes stored in the recording region on the        recording medium.

In this data recording system, when the recording section recordsprimary data, the control section generates an original file. Further,through editing of the original file, a virtual file is prepared.Through use of the virtual file having the edited link data storedthereon, a plurality of files can access at least a portion of theprimary data. As a result, for example, editing of the primary data,such as preparation of a digest of the primary data, becomes feasible,thereby eliminating a necessity for use of two VCRs. Further, theprimary data are managed in the form of only files, thus eliminating anecessity for ensuring a region for use in recording a duplicate of theprimary data.

According to a second aspect of the present invention, the controlsection prepares a virtual file by editing the original file and/or thevirtual file. A virtual file can be formed not only from the originalfile but also from another virtual file.

According to a third aspect of the present invention, there is provideda data recording system for storing primary data, comprising:

-   -   a recording section for recording primary data; and    -   a control section for preparing a file at the time of recording        of the primary data, wherein the file stores, in the form of a        logical address, link data which are formed by arranging in        sequence address data for reproduction purposes stored in a        recording region on a recording medium.

In this data recording system, the file is prepared when the recordingsection records the primary data. As a result of a new file beingprepared by editing the file, editing or reproduction of the primarydata; for example, preparation of a digest of the primary data, becomesfeasible, thereby eliminating a necessity for use of two VCRs. Further,there is eliminated a necessity for ensuring a region for use inrecording a duplicate of the primary data.

According to a fourth aspect of the present invention, the controlsection edits the original file that is prepared at the time ofrecording of the primary data, thereby resulting in preparation of a newfile; that is, a virtual file. Further, a new virtual file is preparedby editing an existing original file and/or an existing virtual file.Reserving of the thus-prepared virtual file enables editing of theprimary data; for example, preparation of a digest of the primary data.

According to a fifth aspect of the present invention, the virtual filecomprises at least a portion of address data pertaining to a file whichis used as a source for editing.

According to a sixth aspect of the present invention, the controlsection prepares a new file on the basis of a plurality of files. A newsingle file can be prepared through editing of a plurality of files.

According to a seventh aspect of the present invention, the address datacorrespond to address data stored in respective unit recording regionswhich are formed by dividing the recording medium into a plurality ofrecording regions.

According to an eighth aspect of the present invention, when any ofexisting files is deleted, the control section deletes the file. When aportion of any one of existing files is deleted, the control sectiondeletes from the file one or a plurality of address data sets pertainingto the file. In this way, any one of existing files or a portion ofthereof can be deleted by deletion of only one or a plurality of addressdata sets pertaining to the file.

According to a ninth aspect of the present invention, the controlsection prepares a link count table for managing the number of timesfiles refers to each of unit recording regions into which the recordingregion on the recording medium is divided. Further, the control sectionupdates data pertaining to the prepared link count table or pertainingto a link count table read from the recording medium, through editingand/or deletion of the files. Reserving the link count table enablesmanagement of the respective unit recording regions. For example, theunit recording region assigned reference number 0 can be released as arecordable region.

According to a tenth aspect of the present invention, the unit recordingregion assigned reference number 0 in the link count table is handled asa recordable region. When the original file prepared at the time ofrecording of the primary data or a portion of the original file isdeleted, the control section resets to zero the reference numberassigned in the link count table to the corresponding unit recordingregions to be deleted. In contrast, when the virtual file prepared byediting the existing file or a portion of the virtual file is deleted,the control section decrements the reference number assigned in the linkcount table to the corresponding unit recording regions to be deleted.As a result, there can be performed processing required fordistinguishing the original file from the virtual file, processing forhandling the virtual file as being in a hierarchy level lower than theoriginal file, and processing for deleting the virtual file.

According to an eleventh aspect of the present invention, when a certainoriginal file or a portion of the original file is deleted, anothervirtual file referring to the corresponding unit recording region to bedeleted is corrected. As a result of correction of another virtual file,another virtual file referring to the corresponding unit recordingregion to be deleted can be prevented from being affected by deletion ofthe certain original file.

According to a twelfth aspect of the present invention, the unitrecording region assigned reference number 0 in the link count table ishandled as a recordable region. When a certain file is wholly orpartially deleted, the control section decrements the reference numberassigned in the link count table to the corresponding unit recordingregions to be deleted, regardless of whether the file to be deleted isan original file prepared at the time of recording of primary data or avirtual file prepared by editing an existing file. As a result, therecan be performed processing required for executing a deleting operation,wherein the original file and the virtual file are handled as being ofthe same hierarchical level.

According to a thirteenth aspect of the present invention, whenoverwriting of the entirety of a certain existing file or overwriting ofa portion of the file is instructed, the control section prepares a newfile with regard to the thus-overwritten primary data, and corrects thelink data stored in the existing files or deletes the existing files. Asa result, processing required for performing an overwriting operationcan be carried out.

According to a fourteenth aspect of the present invention, the controlsection prepares a title set file for storing the address datapertaining to the files and corrects the title set file in response topreparation or deletion of the files.

Reserving of the title set file enables management of the respectivefiles and provides immediate access to the link data pertaining to therespective files.

According to a fifteenth aspect of the present invention, the datarecording system writes at predetermined timing into the recordingmedium data pertaining to the generated, corrected, and deleted files,data pertaining to the link count table, and data pertaining to thetitle set file. At the time of reproduction of the recorded primarydata, the data pertaining to the files, the data pertaining to the linkcount table, and the data pertaining to the title set file are read fromthe recording medium, and the primary data can be reproduced accordingto the thus-read data.

According to a sixteenth aspect of the present invention, the datarecording system reads from the recording medium data pertaining to thefiles, data pertaining to the link count table, and data pertaining tothe title set file, all of which are written into the recording mediumby the data recording system, and stores the thus-read data into astorage section of the data recording system. As a result, the primarydata can be reproduced according to the data pertaining to the files,the data pertaining to the link count table, and the data pertaining tothe title set file, all the data sets being stored in the storagesection.

According to a seventeenth aspect of the present invention, the datarecording system records primary data on and reproduces primary datafrom unit recording regions which are formed by dividing a recordingregion on a recording medium into a plurality of sub-divisions. Datapertaining to a reproduction start frame and a reproduction end frame ofeach unit recording region are stored in the file. Even when the dataare recorded or reproduced on a per-unit-recording-region basis, datacan be edited from an arbitrary position (frame).

According to an eighteenth aspect of the present invention, the datarecording system records primary data on and reproduces primary datafrom unit recording regions which are formed by dividing a recordingregion on a recording medium into a plurality of sub-divisions. Giventhat the minimum rate at which the data recording system transfers datato the recording medium is Be, a bit rate at which data are reproducedis Bd, a time required from the time a head has made a maximum jump overthe recording medium to the time first actual data are acquired is Tw,and the amount of data stored on the unit recording region is C,recording or reproduction of data is performed so as to satisfy therelational expressions (Be−Bd)*Ts>Bd*Tw, Ts=C/Be, and Be>Bd. In thisdata recording system, according to the above relational expressions,data having the amount of (Be−Bd)Ts are stored during period Ts. Thethus-stored data are greater in amount than data in the amount of Bd*Twand are reproduced in Tw, which is a time required from the time a headhas made a maximum jump over the recording medium to the time firstactual data are acquired. Even if the head makes a jump between theinner periphery and the outer periphery of the recording medium, thedata can be stably recorded or reproduced without interruption.

According to a nineteenth aspect of the present invention, there isprovided a data recording method for recording primary data on arecording medium, comprising:

-   -   a step of generating link data by arranging in sequence address        data for reproduction purposes stored in a recording region on        the recording medium;    -   a step of editing existing link data, to thereby generate link        data which differ from the existing link data and sequentially        comprises address data for reproduction; and    -   a step of recording the respective link data sets on the        recording medium.

Through use of the edited link data, a plurality of link data sets canaccess at least a portion of the primary data. As a result, for example,editing of the primary data, such as preparation of a digest of theprimary data, becomes feasible, thereby eliminating a necessity for useof two VCRs and a necessity for ensuring a region for use in recording aduplicate of the primary data.

According to a twentieth aspect of the present invention, there isprovided a method of discretely recording primary data on a recordingmedium, wherein new link data for linking together recording packetsaccording to the recording of the primary data are prepared separatelyfrom the existing link data, and the new link data are recorded on therecording medium together with the existing link data. As a result,various programs can be prepared by means of new link information everytime link information is recorded.

According to a twenty-first aspect of the present invention, when newdata are written over the existing recording packet, the link to therecording packet on which the new data are written is deleted from theexisting link data. Under this data recording method, when new data arewritten over the existing recording packet, the link to the recordingpacket on which the new data are written is deleted from the existinglink data, thereby preventing specification of new recording data fromentering into the existing link data.

According to a twenty-second aspect of the present invention, a linkcount table for managing the number of linked recording packets is alsorecorded on the recording medium. With the foregoing configuration ofthe data recording method, vacant recording packets can also be managedsimultaneous with managing of the linked recording packets. Accordingly,additional recording of data on vacant recording packets can be carriedout smoothly.

According to a twenty-third aspect of the present invention, there isprovided a recording medium having principal data recorded thereon andstoring:

-   -   an original file which is prepared at the time of recording of        the primary data and stores link data which are formed by        arranging in sequence address data for reproduction purposes        stored in a recording region on a recording medium; and a        virtual file which is prepared through editing of the original        file and stores link data formed by arranging in sequence        address data for reproduction purposes stored in the recording        region on the recording medium.

Data are reproduced according to the original file or the virtual filestored in the recording medium, thereby enabling reproduction of data invarious modes, such as a full-reproduction mode or a digest reproductionmode. Further, the data are managed in the form of files, and hence therecording region on the recording medium can be effectively utilized.

According to a twenty-fourth aspect of the present invention, there isprovided a recording medium having primary data recorded thereon andstoring:

-   -   a file which is prepared the time of recording of the primary        data and stores, in the form of a logical address, link data        formed by arranging in sequence address data for reproduction        purposes stored in a recording region on a recording medium.        Preparation of a new file by editing the file enables editing or        reproduction of the primary data; for example, preparation of a        digest of the primary data. Data can be reproduced in various        modes, such as a full-reproduction mode or a digest reproduction        mode. Further, the data are managed in the form of files, and        hence the recording region on the recording medium can be        effectively utilized.

According to a twenty-fifth aspect of the present invention, therecording medium stores

-   -   a new file which is prepared through editing an existing file        and stores, in the form of a logical address, link data formed        by arranging in sequence address data for reproduction purposes        stored in the recording region on the recording medium. Data are        reproduced according to the original file or the virtual file        stored in the recording medium, thereby enabling reproduction of        data in various modes, such as a full-reproduction mode or a        digest reproduction mode.

According to a twenty-sixth aspect of the present invention, therecording medium has stored thereon data pertaining to a title set filefor storing the address data pertaining to the files, and datapertaining to a link count table for managing the number of times filesrefers to each of unit recording regions into which the recording regionon the recording medium is divided. Reserving of the link count tableenables management of the respective unit recording regions. Forexample, the unit recording region assigned reference number 0 can bereleased as a recordable region, and the link data pertaining to therespective files can be accessed immediately.

According to a twenty-seventh aspect of the present invention, there isprovided a recording medium having principal data discretely recordedthereon, wherein there are provided a plurality of types of link datasets for use in linking together respective discretely-recordedrecording packets. By means of the link data sets, the user can enjoyvarious types of reproduction of data; for example, reproduction of datain a full-reproduction mode, a short-time mode, and a digest mode, bydesignation of desired link data.

According to a twenty-eighth aspect of the present invention, therecording medium is provided with data pertaining to a title set filefor specifying a start address of each of the link data sets. By meansof the title set file for specifying a start address of each of the linkdata sets, respectively link data sets can be immediately accessed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing a data recording/reproduction/editingsystem according to the present invention;

FIG. 2 is a block diagram showing memory used in the datarecording/reproduction/editing system;

FIG. 3 is a block diagram showing the configuration of a management datatable;

FIG. 4 is a conceptual view showing a data format of a disk;

FIG. 5 is a descriptive view specifically showing the configuration ofthe management data table;

FIG. 6 is a flowchart showing the recording operation of the datarecording/reproduction/editing system;

FIG. 7 is a flowchart showing the editing operation of the datarecording/reproduction/editing system;

FIG. 8 is a flowchart showing the operation of the datarecording/reproduction/editing system when a title is wholly deletedaccording to a first deleting method;

FIG. 9 is a flowchart showing the operation of the datarecording/reproduction/editing system when a portion of a title isdeleted according to the first deleting method;

FIG. 10 is a flowchart showing the operation of the datarecording/reproduction/editing system when a title is wholly deletedaccording to a second deleting method;

FIG. 11 is a flowchart showing the operation of the datarecording/reproduction/editing system when a portion of a title isdeleted according to the second deleting method;

FIG. 12 is a descriptive view showing the configuration of respectivetitle files for describing the operation of the datarecording/reproduction/editing system;

FIG. 13 is a descriptive view showing the configuration of a managementdata table used in conjunction with the configuration of title fileshown in FIG. 12;

FIG. 14 is a flowchart showing an overwriting operation of the datarecording/reproduction/editing system;

FIG. 15 is a descriptive view showing the configuration of respectivetitle files for describing the overwriting operation of the datarecording/reproduction/editing system;

FIG. 16 is a descriptive view for describing assurance of seamlessreproduction and recording operations of the datarecording/reproduction/editing system;

FIG. 17 is descriptive view for describing variations in the volume ofbuffer at the time of a recording operation;

FIG. 18 is a descriptive view for describing variations in the volume ofbuffer at the time of a reproduction operation;

FIG. 19 is a descriptive view showing the configuration of a managementdata table for describing another feature of the datarecording/reproduction/editing system;

FIG. 20 is a descriptive view showing another configuration of the datamanagement table; and

FIG. 21 is a descriptive view for describing an editing method employedin a conventional video system.

BEST MODE FOR WORKING THE PRESENT INVENTION

As shown in FIG. 1, a data recording/reproduction/editing system Aserving as a data recording system according to the present inventioncomprises a recording signal processing section 10, a magnetic headdrive circuit 12, a magnetic head 14, an optical (pickup) head 16, aspindle motor 18, a servo 20, a reproduction signal processing section22, a monitor 24, buffer memory 26, a system controller 28, an externalinstruction section 30, and memory 32.

The data recording/reproduction/editing system A records audio-visual(AV) data serving as primary data on an optical magnetic disk 40(hereinafter referred to simply as a “disk”) serving as a recordingmedium. The data recording/reproduction/editing system A can reproduceAV data recorded on the magnetic disk 40 and also edit the AV data.

The digital recording processing section 10 subjects AV data input fromthe outside to an encoding operation, addition of an error correctioncode, and a digital modulation operation. The magnetic head drivecircuit 12 drives the magnetic head 14 according to a signal sent fromthe recording signal processing section 10 by way of the buffer memory26. The magnetic head 14 magnetizes a recording film placed on the disk40 and is used for recording AV data on the recording film. The opticalhead 16 has a semiconductor laser. At the time of recording, a laserbeam is emitted from the semiconductor laser. At the time ofreproduction, a laser beam is radiated onto the disk 40, and lightreflected from the disk 40 is received by the optical head 16. A head 17is constituted by the magnetic head 14 and the optical head 16.

The spindle motor 18 rotatively drives the disk 40 at a predeterminedrotational speed, and the servo 20 controls the number of rotations ofthe spindle motor 18 and effects servo control operations such as afocusing servo operation, a tracking servo operation, a spindle servooperation, and a thread servo operation. The reproduction signalprocessing section 22 subjects the signal read from the buffer memory 26to digital demodulation, error correction, or decoding. The monitor 24outputs, in the form of an image or sound, the signal processed by thereproduction signal processing section 22.

The buffer memory 26 records the AV data onto the disk 40 andtemporarily stores AV data when the AV data are reproduced from the disk40. The system controller 28 controls the overall datarecording/reproduction/editing system; i.e., operation of individualsections of the data recording/reproduction/editing system A. Theexternal instruction section 30 is used when the user performs variousoperations.

As shown in FIG. 2, the memory 32 has a program storage section 34 and amanagement data table storage section 36. The program storage section 34stores an application program which governs the operation of the datarecording/reproduction/editing system A. More specifically, the programstorage section 34 stores a program for executing operations pertainingto a flowchart shown in FIGS. 6 through 11. The management data tablestorage section 36 stores a management data table to be described later.

The magnetic head drive section 12, the head 17, and the servo 20 act asa recording section, and the system controller 28 acts as a controlsection.

A data format of the disk 40 will now be described.

As shown in FIG. 4, main storage of the disk 40 is divided into blocks;that is, N containers 100 (where N is a natural number). Each container100 constitutes a data block comprising a predetermined number of bits.Preferably, the number of bits corresponds to the amount of data whoserecording and reproduction requires a few seconds. The container 100corresponds to a unit recording region. In the datarecording/reproduction/editing system, AV data are subjected to editing,such as recording of the AV data on the disk 40 or reproduction of theAV data from the disk 40, on a per-container basis. A management regionused for recording the management data table is ensured along theinnermost periphery of the disk 40.

The structure of data provided in the management data table will now bedescribed.

As shown in FIG. 3, the management data table 200 comprises a title setfile 202, a title file 204, and a link count table 206.

The title set file 202 manages a title file and comprises headerinformation and start addresses of respective title files. For example,a title set file which is shown in FIG. 5 and entitled “Title 0Descriptor” stores a start address of a title file 204-1. FIG. 5 is adiagram conceptually showing a specific example of the management datatable.

The title file 204 stores link data pertaining to the title file. Morespecifically, as shown in FIG. 5, the title file 204 sequentially storesheader data and address data pertaining to starting positions ofrespective containers on the disk 40 (hereinafter referred to simply as“container address data”). For instance, address data pertaining to thehead sector of a container are stored in the title file 204. The addressdata are defined as a logic address. The address data are used forreproducing AV data and the address data pertaining to the respectivecontainers are arranged in sequence of reproduction. In short, datapertaining to a sequence (or link) in which AV data are stored in thecontainer 100 are reproduced. The title file corresponds to a term“file” used in the disclosure of the invention and claims appendedhereto.

For example, in the title file 204-1, container numbers are specified insequence of C2→C4→C5, to thereby specify sequence of reproduction. Inthe title file 204-1 shown in FIG. 5, “pointer 0” designates addressdata pertaining to container C4. In this way, the corresponding linkedcontainers are specified for each title file, with the result that oneAV program is composed for each title file. The header data comprisedata pertaining to a title and data pertaining as to whether the file isan original file or a virtual file. The original file and the virtualfile will be described later. A plurality of title files can be retainedfor a single title set file 202.

The containers managed under the title file may involve an overlapwithin a single title file or an overlap between title files. Forexample, as shown in FIG. 5, container C4 is referred to by the titlefile 204-1 of title 0 and a title file 204-2 of title 1. This casecorresponds to a container which involves overlap between containerbetween the title files. Alternatively, after a certain container hasbeen specified by a certain title file, the container may be specifiedagain.

The title file may be divided into an original file and a virtual file.The original file is produced or prepared when AV data are recorded. Incontrast, a virtual file is prepared or produced after recorded AV datahave been subjected to edition processing to be described later.

The link count table 206 shows the number of times title files refer toan individual container (hereinafter referred to simply as a “referencenumber”). If the reference number of a certain container is 0, thecontainer can be recorded. In FIG. 5, no title file refers to containerC1 as well as to C3. The reference number of a container assumes a valueof 0 when no AV data have been recorded in a container at any time orwhen the user has deleted recorded data from a container. The operationof deletion will be described later. In a case where the referencenumber of a certain container has a value of one or more, the containeris referred to by at least any one of the title files and constitutes aprogram. Therefore, such a container cannot be recorded. In FIG. 5, forexample, two title files refer to container C4, and hence the referencenumber of container C4 is 2.

As mentioned above, the management data table manages the sequence ofreproduction of containers and enables reproduction of the images and/orsounds desired by the user.

When a disk having the management data table recorded thereon is loadedto the data recording/reproduction/editing system A, the management datatable is read first and stored in the memory 32.

Next, the operation of the data recording/reproduction/editing system Awill be described.

First, by reference to FIG. 6 and like drawings, an explanation is givenof recording of AV data to the disk 40. Although various types of AVdata are conceivable as AV data to be recorded, AV data pertaining to abroadcast, for example, are employed.

The user instructs recording by way of the external instruction section30 (S10), and the system controller 28 refers to the link counter table206 stored in the memory 32 and ensures a recordable region (S11). Inother words, the system controller 28 finds a container to which notitle file refers. When the disk is loaded into the datarecording/reproduction/editing system A, data pertaining to themanagement data table stored in the disk 40 are read and stored into thememory 32. In the case of a virgin disk having no data recorded thereon,since a management data table is not recorded, data can be sequentiallyrecorded on the disk from the first container. If the loaded disk 40 isa virgin disk and data pertaining to a management data table are notread from the disk 40, a link count table in which all the referencenumbers of containers have a value of 0 is retained in the memory 32.Simultaneously, a title set file having no data recorded therein isretained in the memory 32. AV data are then sequentially recorded onrecordable containers (S12).

At the time of recording of data, the following recording operations areperformed. In the recording signal processing section 10, AV data inputfrom the outside are subjected to an encoding operation, addition of anerror correction code, and a digital modulation operation. Thethus-processed AV data are written in the buffer memory 26. The buffermemory 26 performs a buffering operation so that the AV data can berecorded on the disk 40 on a per-container basis. More specifically, anAV data transfer rate (corresponding to a rate at which AV data arewritten into the buffer memory 26) is set so as to be higher than a rateat which AV data are recorded on the disk 40 or a rate at which AV dataare reproduced from the disk 40 (corresponding to a rate at which AVdata are reproduced from the buffer memory 26). The AV data areconsecutively written into the buffer memory 26, whereas the AV data areintermittently read from the buffer memory 26. The thus-read AV data areinput to the magnetic head drive circuit 12 and are recorded on the disk40 on a per-container basis through use of the magnetic head 14 and theoptical head 16.

In step S11, since the system controller 28 is retrieving a recordablecontainer by reference to the link count table 206, the systemcontroller 28 controls the servo 20 such that the AV data are recordedin a container to which no title file refers.

Next, the user instructs termination of recording (S13), and therecording operation is terminated (S14). The link count table isupdated, a title file is generated, and the title set file is updated(S15).

In the link count table 206, the container on which AV data are newlyrecorded is assigned 1 as a reference number.

A new title file is generated, and header data pertaining to the titlefile are generated according to details (for example, a title) specifiedby the user by way of the external instruction section 30. Datapertaining to the start address of the container on which AV data arerecorded are added to the header data as a sequential pointer. Aspecific symbol is embedded as a final pointer in a final container sothat the container can be identified as the final container. The titlefile that has been subjected to such a recording process is taken as anoriginal file. Preferably, data indicating that the title file is anoriginal file are written into the header data pertaining to the titlefile. The process for generating, at the time of recording of principaldata, such an original file corresponds to a “process for generatinglink data which comprise address data for reproduction purposes arrangedin sequence in a recording area of a recording medium.”

The start address of a new title file is stored in the title set file asa “title ‘n’ descriptor.”

For example, as shown in FIG. 12, when AV data are recorded oncontainers C1 to C10, all of which are assigned 0 as a reference number,containers C1 to C10 are written as link data into a title file to benewly produced (this title file is taken as a zero-th title file). Thezero-th title file shown in FIG. 12 corresponds to an original file. Ata point in time when only the zero-th title file is produced, containersC1 to C10 in the link count table are assigned 1 as a reference number.

If termination of recording is instructed at any point of a certaincontainer, recording is continued to some extent even after instructionfor termination of recording, because recording is effected on aper-container basis.

Data pertaining to the title file produced through recording, an updatedtitle set file, and a updated link count table; that is, data pertainingto a management data table, are written into a management region alongthe innermost periphery of the disk according to an instruction forremoval of the disk. The process for writing title file data correspondsto a “process for recording link data onto a recording medium.” In thecase of a virgin disk, a title set file and a link count table, as wellas title file data, are newly written into the management region.Although a single title set file is sufficient for recording amanagement information table on a certain disk, a plurality of title setfiles may also be written on the disk.

If recording is terminated at any point of a certain container, theremaining area of the container must be padded, because data arerecorded on a per-container basis in the present embodiment. Theprocessing relating to step S15 may be performed not after recording ofdata but during the course of recording of data.

The operation of the data recording/reproduction/editing system A at thetime of edition of AV data recorded on the disk 40 will now be describedby reference to FIG. 7 and like drawings. The following editingoperation can be employed in, for example, a case where a digest of AVdata pertaining to a certain program is created.

By way of the external instruction section 30, the user selects one ofthe reserved title files (S20). For example, according to the managementdata table stored in the memory 32, a list of title files is displayedon the monitor 24, and the user selects an arbitrary title file from thelist by way of the external instruction section 30. At the time ofindication of the title file list, the system controller 28 reads data(e.g., a title) reserved in the header data pertaining to the title filefrom the memory 32 and displays the thus-read data on the monitor 24.

The user then specifies an editing start point (S21). Specifically, itis contemplated that while AV data are reproduced according to the linkdata pertaining to a selected title file, the user performs specifyingaction at a desired editing start point by way of the externalinstruction 30. Next, the user specifies an editing end point (S22).Specifically, it is contemplated that while AV data are reproducedaccording to the link data pertaining to the selected title tile, theuser performs specifying action at a desired editing end point.Alternatively, an editing start point and an editing end point may bedetermined on the basis of a time that is to lapse from the start of arecording area or on the basis of the amount of data from the start of arecording area. If the user specifies an editing start point or anediting end point at halfway position in a certain container, containerscorresponding to the thus-specified editing start and end points may beincluded as containers to be subjected to editing. Alternatively, at anediting start time, a container after the container corresponding to theediting start time may be subjected to editing, and a container beforethe container corresponding to the editing end time may be subjected toediting.

The user determines whether to edit another portion with regard to thesame title file (S23). If another portion is edited with regard to thesame title file, processing returns to step S21. In contrast, if theuser does not edit any other portion with regard to the same title file,the user determines whether to edit another title file (S24). If theuser edits another title file, processing returns to step S20, where theuser can edit a plurality of title files, as well as a plurality ofcontainers with regard to the same title file. If the user does not editany other tile file in step S24, the link count table is updated, atitle file is generated, and the title set file is updated (S25).

In the link count table, the reference number of each of the containersto which the title file has newly referred is incremented by one. If anew title file refers to a certain container a plurality of times, thereference number of the container is incremented by an amountcorresponding to the number of times the container has been referred to.

A new title file is generated in the memory 32, and header datapertaining to the title file are produced according to details (forexample, a title) specified by the user by way of the externalinstruction section 30. The address data pertaining to the containerthat has been edited is added to the header data as a sequentialpointer. The address data pertaining to the container may be selectedfrom the data reserved in the title file selected in step S20. Morespecifically, the address data pertaining to the container are formedfrom at least a portion of a series of address data sets reserved in thetitle file which is used as a source for editing. A special symbol isembedded as a final pointer in a final container so that the containercan be identified as the final container.

The start address of a new title file is stored in the title set file asa “title ‘n’ descriptor.”

Processing pertaining to a flowchart shown in FIG. 7 is essentiallycontrolled by the system controller 28 according to a program reservedin the memory 32.

For example, in an example shown in FIG. 12, a first title file isproduced through the following processing operation. Specifically, thezero-th title file is selected, and starting of editing is instructed atthe position of container C3 (S21). Termination of editing is instructedat the position of container C5 (S22). In order to edit containers C8 toC10, processing again returns to step S21 from step S23, thus specifyingcontainers C8 to C10. Since no other title file is edited in step S24,processing proceeds to step S25. At a point in time when the zero-thtitle file and the first title file are produced, the reference numberassigned to containers C3 to C5 and C8 to C10 in the link count table is2.

In the example shown in FIG. 12, the second title file is producedthrough the following processing. First, the zero-th title file isselected (S20), and containers C1 and C2 are specified (S21 and S22). Inorder to edit the first title file, processing returns to step S20 fromsteps S23 and S24. The first title file is then selected. Subsequently,containers C8 to C10 are specified (S21 and S22), and processingproceeds to steps S23, S24, and S25. At a point in time when the zero-thtitle file, the first title tile, and the second title file areproduced, the reference number assigned to each of containers C1 to C5in the link count table becomes 2. The reference number assigned to eachof containers C8 to C10 becomes 3. Although in the foregoing descriptionat the time of editing of containers C8 to C10 in the second title filethe first title file is edited first, the zero-th title file may beedited first.

The first and second title files shown in FIG. 12 are virtual files.Preferably, data indicating that title files are virtual files arewritten in header data pertaining to the respective title files. Theprocess for generating such virtual files corresponds to a “process forgenerating link data which differ from existing link data and comprisereproduction address data sets arranged in sequence in a recording areaof a recording medium, by editing of existing link data.”

Updating of the link count table in step S25 or updating of a title setfile in step S25 may be sequentially performed during editing. In thepresent embodiment, AV data are edited on a per-container basis.

As shown in FIG. 12, in the zero-th title file serving as the originalfile, address data are sequentially linked to continuous containers.Even in the original file, naturally there is a case where containers tobe linked according to address data are discretely recorded on the disk.FIG. 12 can be said to show a plurality of types of link data forlinking discretely-recorded packets together.

In contrast with the foregoing case, if the original sequence ofreproduction may be discarded at the time of editing of AV data, addressdata pertaining to the title file may be updated in a newly-editedsequence of reproduction. In other words, the existing title file isreplaced with a title file having new link data. If reproduction of somecontainers becomes unnecessary as a result of changing of the sequenceof reproduction to a new sequence of reproduction, the reference numberassigned to those containers in the link count table is decremented.Through the foregoing operations, virtual edition of AV data is carriedout.

Data pertaining to the title file produced through the foregoing editingoperations and data pertaining to the updated title set file and theupdated link count table are written into the management region alongthe innermost periphery of the disk according to an instruction forremoval of the disk. The processing for writing data onto the title filecorresponds to a “process for recording link data on a recordingmedium.” In a disk which has been found not to have a title set file ora link count table recorded thereon at the time of being loaded into thedata recording/reproduction/editing system A, a tile set file and a linkcount table are also newly written into the management region.

The operation of the data recording/reproduction/editing system A whenthe AV data recorded on the disk 40 are reproduced will now bedescribed.

First, the user selects one title file to be reproduced from among thereserved title files, by way of the external instruction section 30. Forexample, according to the management data table reserved in the memory32, a list of title files are displayed on the monitor 24, and the userselects an arbitrary title file by way of the external instructionsection 30.

Data indicating which of the title files is selected are sent from theexternal instruction section 30 to the system controller 28, and thesystem controller 28 controls the servo 20 so as to access apredetermined container on the basis of the address data pertaining to acontainer stored in the selected title file. The servo 20 controls theoptical head 16 and the spindle motor 18. The optical head 16 emits alaser beam and receives light reflected from the recording surface ofthe disk 40, to thereby read the AV data recorded on the disk 40. Forexample, in the example shown in FIG. 12, in a case where the firsttitle file is selected, AV data are read out from containers in thesequence of C3, C4, C5, C8, C9, and C10. If an instruction forspecifying a title file to be reproduced is not entered by way of theexternal instruction section 30, a title file located at the head of thetitle set file is reproduced. For example, in the case shown in FIG. 5,according to the address data reserved in the title file 204-1 of title0, containers are accessed from the top in sequence of point 0, pointer1, pointer 2, . . . .

The thus-read AV data are temporarily stored in the buffer memory 26. Atthis time, the rate at which the AV data are written into the buffermemory 26 and the rate at which the AV data are read from the buffermemory 26 are switched in relation to the case at the time of recording.Specifically, the AV data are intermittently written into the buffermemory 26 at the rate at which the AV data are recorded on or reproducedfrom the disk 40 (corresponding to the rate at which the AV data arewritten into the buffer memory 26), and the AV data are read from thebuffer memory 26 at a rate at which the AV data are transferred(corresponding to a rate at which the AV data are read from the buffermemory 26).

The AV data read from the buffer memory 26 are subjected to digitaldemodulation, error correction, and decoding in the reproduction signalprocessing section 22, and the thus-processed data are output by way ofthe monitor 24.

An explanation will now be given of deletion of a title file or erasureof a portion of a title file.

Two methods are conceivable for deleting a title file or a portion of atitle file. According to a first deleting method, an original file isdistinguished from a virtual file. The virtual file is handled as beingof a lower hierarchical level than the original file. When the originalfile is deleted, a portion of the virtual file which is referred to isalso deleted. According to a second deleting method, an original fileand a virtual file are handled as being of the same hierarchical level.Even if the original file is deleted, a portion of the virtual filewhich is referred to is not deleted.

The first deleting method will now be described. Deletion of a titlefile on a per-title basis will first be described by reference to FIG. 8and like drawings.

The user selects one of the reserved title files and instructs deletionof the thus-selected title file by way of the external instructionsection 30 (S30). For example, according to the management data tablereserved in the memory 32, a list of title files is displayed on themonitor 24. By way of the external instruction section 30, the userselects an arbitrary title file and instructs deletion of thethus-selected title file. At the time of indication of the list of titlefiles, the system controller 28 reads from the memory 32 data (e.g., atitle) reserved in the header data pertaining to the title file anddisplays the thus-read data on the monitor 24.

A determination is then made as to whether or not the selected titlefile is an original file or a virtual file (S31). Since the dataindicating whether the title file is an original file or a virtual fileare stored in the header data pertaining to the title file, the systemcontroller 28 can make a determination on the basis of the data. If thetitle file is determined to be an original file, processing proceeds tostep S32. In contrast, if the title file is determined to a virtualfile, processing proceeds to step S36.

In step S32, the specified title file is deleted from the memory 32.

Subsequently, the title set file 202 is corrected (S33). Specifically,data pertaining to a title file to be deleted are deleted.

Further the link count table 206 is corrected (S34). The referencenumber assigned to the containers to which the deleted title file hasreferred is reset to 0, and these containers are opened as recordableareas.

The title file of a virtual file which refers to any portion of thedeleted title file is corrected or deleted (S35). If a certain titlefile refers to only a container referred to by the title file to bedeleted, the title file is deleted. Alternatively, if a certain titlefile refers to a container to which the title file to be deleted refersand to another container, the contents of the title file are corrected.

In contrast, if in step S31 the title file is determined to be a virtualfile, processing proceeds to step S36, and the specified title file isdeleted from the memory 32.

Next, the title set file 202 is corrected (S37). Data pertaining to thetitle file to be deleted are deleted.

The link count table 206 is corrected (S38). The reference numberassigned to the containers referred to by the deleted title file isdecremented by one. If the deleted title file refers to a certaincontainer a plurality of times, the reference number assigned to thecontainer is decremented by an amount corresponding to the number oftimes the container is referred to. In this regard, the same applies toprocessing pertaining to step S53 to be described later.

Specific processing will be described by reference to the example shownin FIG. 12. In FIG. 12, a third title file is an original file whichrefers to containers C11 to C13. Further, a fourth title file is avirtual file which refers to containers C7 to C13. Containers C7 to C13correspond to containers obtained through editing of the zero-th titlefile, and containers C8 to C13 correspond to containers obtained throughediting of the third title file. FIG. 13 shows correspondence among thelink count table, the title set files, and the title files shown in FIG.12. The link count table shown in FIG. 13 shows a case where AV data arestored in the zero-th title file to the second title files.

In a case where the zero-th title file is deleted, since the zero-thtitle file is an original file, processing proceeds to step S32, wherethe zero-th title file is deleted from the memory 32 (S32). The datapertaining to the zero-th title file are deleted from the title set file202 (S33). In the link reference table, the count number assigned tocontainers C1 to C10 is reset to 0 (S34). Through processing pertainingto step S35, the first title file and the second title file are deletedfrom the memory 32. From the fourth title file, address data pertainingto containers C7 to C10 are deleted, and address data pertaining tocontainers C11 to C13 are stored into the fourth title file. The thirdtitle file is left, exactly as is.

In a case where the first title file is deleted, sine the first titlefile is a virtual file, processing proceeds to step S36, where the firsttitle file is deleted from the memory 32. Data pertaining to the firsttitle file are deleted from the title set file 202 (S37). In the linkcount table, the reference number assigned to each of containers C3 toC15 and C8 to C10 is decremented by one (S38).

When the third title file is deleted, the link data pertaining to thefourth title file are corrected to containers C7 to C10.

Deletion of a portion of the title file according to the first deletingmethod will now be described by reference to FIG. 9 and like drawings.In this case, not the entirety of a certain title file is deleted, but aportion of a title file is deleted. In this case, there is performedprocessing substantially identical with that employed for deleting atitle file on a per-file basis. The difference between deletion of atitle file and deletion of a portion of a title file resides in thatdeletion of a portion of a title file does not involve an amendment ofthe title set file.

First, the user selects one of the reserved title files and instructsdeletion of the thus-selected title file by way of the externalinstruction section 30 (S40). For example, according to the managementdata table stored in the memory 32, a list of title files is displayedon the monitor 24, and the user selects an arbitrary title by way of theexternal instruction section 30 and specifies deletion start and endpoints. Conceivable measures for specifying the deletion start and endpoints include a method of specifying the deletion start and end pointswhile AV data are reproduced, and a method of specifying a deletionstart point and a deletion end point on the basis of a time that is tolapse from the start of a recording area or on the basis of the amountof data from the start of recording area. At the time of indication ofthe title file list, the system controller 28 reads from the memory 32data (e.g., a title) reserved in the header data pertaining to the titlefile and displays the thus-read data on the monitor 24.

A determination is then made as to whether or not the selected titlefile is an original file or a virtual file (S41). Since the dataindicating whether the title file is an original file or a virtual fileare stored in the header data pertaining to the title file, the systemcontroller 28 can make a determination on the basis of the data. If thetitle file is determined to be an original file, processing proceeds tostep S42. In contrast, if the title file is determined to be a virtualfile, processing proceeds to step S45.

In step S42, the specified title file is corrected. In other words, theaddress data pertaining to containers located in the region to bedeleted are deleted.

Further, the link count table 206 is corrected (S43). The referencenumber assigned to the containers located in the region to be deleted isreset to 0, and these containers are released as recordable areas.

The title file of a virtual file which refers to any portion of theregion to be deleted is corrected or deleted (S44). If a certain titlefile refers to only the containers located in the region to be deleted,the title file is deleted. Alternatively, if a certain title file refersto containers located in the region to be deleted and to anothercontainer, the contents of the title file are corrected.

In contrast, if in step S41 the title file is determined to be a virtualfile, processing proceeds to step S45, and the specified title file iscorrected. In other words, the address data pertaining to the containerslocated in the region to be deleted are deleted.

The link count table 206 is corrected (S46). The reference numberassigned to the containers located in the region to be deleted isdecremented by one. If a certain container located in the region to bedeleted is referred to a plurality of times, the reference numberassigned to the container is decremented by an amount corresponding tothe number of times the container is referred to. In this regard, thesame applies to processing pertaining to step S62 to be described later.

Specific processing will be described by reference to the example shownin FIG. 12.

In a case where containers C3 and C4 of the zero-th title are deleted,since the zero-th title is the original file, processing proceeds tostep S42, where the zero-th title file is corrected (S42). Specifically,address data pertaining to containers C3 and C4 are deleted, and addressdata pertaining to container C5 comes to fall next to the address datapertaining to container C2. In the link count table, the count numberassigned to containers C3 and C4 is =reset to 0 (S43). Throughprocessing relating to step S44, address data pertaining to containersC2 and C3 are deleted from the first title file such that the addressdata pertaining to container C5 comes to fall at the beginning of thefirst title file. When containers C3 to C5 of the zero-th title file aredeleted, the address data stored in the first title file are alsocompletely deleted, in turn resulting in deletion of the first titlefile itself.

In the case of deletion of containers C3 and C4 of the first title file,since the title file is a virtual file, processing proceeds to step S45,where address data pertaining to containers C2 and C3 are deleted fromthe first title file such that the address data pertaining to containerC5 comes to fall at the beginning of the first title file. In the linkcount table, the reference number assigned to containers C3 and C4 isdecremented by one (S46).

The second deleting method will now be described. Deletion of a titlefile on a per-title basis will first be described by reference to FIG.10 and like drawings.

The user selects one of the reserved title files and instructs deletionof the thus-selected title file by way of the external instructionsection 30 (S50). Even in this case, as in the case of the processingrelating to step C30 and C40, according to, for example, the managementdata table reserved in the memory 32, a list of title files is displayedon the monitor 24. By way of the external instruction section 30, theuser selects an arbitrary title file and instructs deletion of thethus-selected title file. At the time of indication of the list of titlefiles, the system controller 28 reads from the memory 32 data (e.g., atitle) reserved in the header data pertaining to the title file anddisplays the thus-read data on the monitor 24.

The specified title file is deleted from the memory 32 (S51).

Next, the title set file 202 is corrected (S52); information about thetitle set file which is an object of deletion is deleted.

Subsequently, the title set file 202 is corrected (S53). Specifically,the reference number assigned to the containers referred to by thedeleted title file is decremented by one. The containers whose referencenumber becomes 0 as a result of decrement of the reference number arereleased as recordable areas.

According to the second deleting method, since an original file and avirtual file are handled as being of the same hierarchical level, theoriginal file is not distinguished from the virtual file.

Specific processing will be described by reference to the example shownin FIG. 12.

For example, when the zero-th title file is selected and deleted, thezero-th title file is deleted from memory 32 (S51). Data pertaining tothe zero-th title file are deleted from the title set file 202 (S51). Inthe link count table, the reference number assigned to containers C1 toC10 is decremented by one (S53). As shown in FIG. 12, if the zero-thtitle file is deleted while the zero-th title file through the fourthtitle file are recorded in the disk, the reference number assigned to,for example, containers C1 to C5 is decremented from two to one; thereference number assigned to container C6 is decremented to zero; thereference number assigned to container C7 is decremented from two toone; and the reference number assigned to containers C8 to C10 isdecremented from three to two.

Deletion of a portion of the title file according to the second deletingmethod will be described by reference to FIG. 11 and like drawing. Inthis case, not the entirety of a certain title file, but a portion ofthe title file is deleted.

Even in this case, processing substantially identical with that used fordeleting the entire title file is performed. Since, the entirety of thetitle file is not intended to be deleted, the processing for deleting aportion of a title file differs from the processing for deleting theentirety of a title file in that a title set file is not corrected.

First, the user selects one of the reserved title files and instructsdeletion of the thus-selected title file by way of the externalinstruction section 30 (S60). For example, according to the managementdata table stored in the memory 32, a list of title files is displayedon the monitor 24, and the user selects an arbitrary title by way of theexternal instruction section 30 and specifies deletion start and endpoints. Conceivable measures for specifying the deletion start and endpoints include a method for specifying the deletion start and end pointswhile AV data are reproduced and a method of specifying a deletion startpoint and a deletion end point on the basis of a time that is to lapsefrom the start of a recording area or on the basis of the amount of datafrom the start of recording area.

The thus-specified title file is corrected (S61). Specifically, theaddress data pertaining to containers located in the region to bedeleted are deleted.

Next, the link count table 206 is corrected (S62). Specifically, thereference number assigned to the containers referred to by the deletedtitle file is decremented by one. The containers whose reference numberbecomes 0 as a result of decrement of the reference number are releasedas recordable areas.

Specific processing will be described by reference to the example shownin FIG. 12.

In a case where containers C3 and C4 of the zero-th title are deleted,the zero-th title file is corrected (S61). Specifically, address datapertaining to containers C3 and C4 are deleted, and address datapertaining to container C5 comes to fall next to the address datapertaining to container C2. In the link count table, the referencenumber assigned to containers C3 and C4 is decremented by one (S62). Inthe example shown in FIG. 12, the reference number assigned tocontainers C3 and C4 is decremented from two to one.

The contents of the management data table modified through deletion of atitle file are written into the management region along the innermostperiphery of the disk according to an instruction for removal of thedisk.

As a result of deletion of a title file, containers whose referencenumber has become zero can be recorded. As mentioned above, the datarecording/reproduction/editing system A is provided with the link counttable for managing the reference number of each title tile, to therebyenable management of vacant containers. Consequently, recording of AVdata in vacant containers can be performed smoothly.

In contrast with the foregoing case, in a case where another data set iswritten over a container already having AV data recorded thereon bysimultaneously performing deletion of the already existing AV data andwriting of another data set, the following processing is performed.

As shown in FIG. 14, the user selects one of the reserved title filesand instructs overwriting of data on the thus-selected title file by wayof the external instruction section 30 (S70). In this case, in order toeffect overwriting, an original file is selected. Further, in order toenable data to be written over at any point of the title file, therecording/reproduction/editing system A may be configured so that theuser can select a recording start position.

Recording of data is now carried out (S71). If no recording startposition is specified, data are recorded on the first container linkedto the title file. Subsequently, data are recorded in containers in thesequence indicated by the link data pertaining to the title file.

When the user instructs termination of recording (S72), recording ofdata is completed (S73).

A title file for the newly-recorded AV data is produced, and the titlefile to be overwritten is corrected or deleted (S74). Further, the titleset file is updated, and a virtual file which refers to thethus-overwritten title file is corrected or deleted (S74).

Specific processing will now be described by reference to FIG. 15. InFIG. 15, the zero-th title file is an original file and is linked tocontainers C1 to C10. The first title file is produced through editingand refers to containers C6 to C8.

The following explanation is based on the condition that the userinstructs overwriting of the zero-th title file (S70) and overwriting ofdata from container C3; specifically, the explanation is based on thecondition that the user instructs sequential recording of data fromcontainer C3 to container C6.

Newly recorded AV data are recorded in containers C3 to C6, and a newtitle file; that is, a second title file, is produced (S74). Addressdata serving as link data pertaining to the second title file are storedin containers C3 to C6. A special symbol representing a final containeris embedded in the position of a pointer of address data pertaining tocontainer C6.

In the zero-th title file, AV data are written over containers C3 to C6,whereby the address data pertaining to containers C3 to C6 are deleted.As a result, address data pertaining to container C7 comes to fall nextto address data pertaining to container C2. In association withgeneration of the new second title file, data pertaining to the secondtitle file are written into the title set file 202, whereby the titleset file 202 is updated. Since the AV data of container C6 to which thefirst title file refers are overwritten, the address data pertaining tocontainer C6 are deleted, with the result that address data pertainingto container C7 come to fall at the head of the first title file. Inthis way, specification of newly-recorded AV data can be prevented fromentering into the existing link data.

In a case where AV data are written over up to container C10, sincecontainer C2 is the final container of the zero-th title file, a specialsymbol representing a final pointer is embedded in the position of theaddress data pertaining to container C2. In this case, all thecontainers to which the first title file refers are overwritten, andhence the first title file is deleted.

If, of the pointers of the existing title files, new AV data are writtenover pointers which are spaced at intervals, the overwritten pointersare packed. More specifically, the title file is reconfigured bysequentially moving the pointers, which are not overwritten, to higherhierarchical levels so as to form a consecutive group of pointers and byembedding a special symbol representing a final pointer in a positionsubsequent to the group of pointers. In containers which are shown inFIG. 15 and taken as an example, if data are written over containers C3,C5, and C7, in this sequence, address data pertaining to container C4are moved so as to fall next to address data pertaining to container C2in the zero-th title file.

Further, the pointer of the title file may be utilized as a time table.A time required for recording AV data in a container is set to apredetermined time. The only requirement is to count pointers at thetime of a fast-forwarding operation, a rewinding operation, and a timesearch operation. For example, if a time required for recording data ina single container assumes a value of two seconds, a container in whichdata will be recorded after lapse of ten seconds can be searched byfinding only the fifth pointer.

If the time required for recording data in a container assumes a valueof one second or less, pointers can also be utilized for indicating atime during recording and reproduction operations. For example, in acase where a count time is displayed every second at the time ofrecording or reproduction, one second is counted only when a pointer isdetected. If the time required for recording data into a containerassumes a value of 0.5 seconds, one second is counted only when twopointers are detected.

In order to ensure seamless recording or reproduction of data, the datarecording/reproduction/editing system A performs the followingprocessing.

Given that the minimum transfer rate of the datarecording/reproduction/editing system A is Be, a bit rate at which AVdata are reproduced is Bd, a worst value of a jump (seek) time is Tj, atime during which the disk 40 waits for rotation is Tr, an expected timerequired for shock resistance is Tp, a maximum time required forcorrecting errors in the AV data that have been read is Te, and theamount of storage on a container is C, recording or reproduction of AVdata is performed so as to satisfy the relational expression(Be−Bd)*Ts>Bd*Tw. In other words, recording and reproduction of AV dataare performed such that the product of (Be−Bd) and Ts becomes greaterthan the product of Bd and Tw, where Ts=C/Be, Tw=Tj+Tr+Tp+Te, and Be>Bd.

Here, Tj represents the maximum time required for the optical head tojump between the inner periphery and the outer periphery of a recordableregion of the disk 40. The distance between the inner periphery and theouter periphery of a recordable region of the disk corresponds to themaximum jump distance. Shock resistance is ensured beforehand as a timeduring which the head 17 is unable to perform any recording orreproduction operation if physical impact is imparted to the head 17. Tpcorresponds to an expected time which is ensured beforehand and includesthe time for attaining shock resistance. ECC (error correction code) andEDC (error detecting code) processing operations are required beforedata to be actually stored in the buffer memory 26 are obtained fromactual data which are read from the disk 40 after jumping of the head17. For this reason, the worst value (Te) of a group delay time requiredfor the ECC and EDC processing operations is employed as a factor ofdetermining Tw. In short, Tw represents a time required from the timethe head has made a maximum jump over the disk 40 to the time firstactual data are acquired.

Recording and reproduction of data are carried out on the basis of theminimum rotation rate Be satisfying the foregoing relational expression,the worst value Tj of the jump (seek) time, the worst value Tr of therotational latency, the expected time tp including the time forattaining shock resistance, the maximum time Te required for correctingdata which are read, the reproduction bit rate Bd, and the amount C ofstorage on a container.

More specifically, AV data are written in the buffer memory 26 at thebit rate Bd. Simultaneously, the AV data are read from the buffer memory26 at the bit rate Be, and the thus-read AV data are sent to themagnetic head drive circuit 12 (see FIG. 16). When the AV data arerecorded on the disk 40, the AV data are sequentially recorded in units,each unit comprising the amount C of storage on a container. The AVplayer module shown in FIG. 16 is included in the record signalprocessing section 10 or the reproduction signal processing section 22shown in FIG. 1.

As mentioned above, the relationship Be>Bd is maintained, and if aplurality of containers are sequentially recordable, variations arise inthe amount of buffer during period Ts in which AV data are recorded inarbitrary containers, such as those appearing in period AB, period BC,and period EF. In period AB, period BC, and period EF shown in FIG. 17,the amount of buffer is illustrated to drop after exhibiting anincrease. In reality, data are written into the buffer memory 26simultaneous with reading of data from the buffer memory 26. SinceBe>Bd, all the AV data that are written into the buffer memory 26 duringperiod Ts are recorded on the disk 40.

If a plurality of containers are not continuously recordable, the head17 must be moved so as to jump over unrecordable containers torecordable containers. At the time of jump, AV data are written into thebuffer memory 26, but naturally the AV data are not written into thedisk 40. Because of the relational expression Tw=Tj+Tr+Tp+Te, the timerequired from the time the head 17 is moved to an arbitrary region inthe recordable region of the disk 40 to the time first actual data areacquired does not exceed Tw. The maximum jump time corresponds to Tw.Because of a relationship (Be−Bd)*Ts>Bd*Tw, even if the head 17 isjumped while writing AV data into the disk 40 is disabled only duringperiod Tw, all the AV data that have been stored during period Tw can bewritten into a container, to which the head 17 is jumped, within theperiod of Ts. This can be derived as follows; namely, Bd*Tw on the rightside of the relational expression represents the amount of data storedin the buffer memory 26 during the jump time; (Be−Bd)*Ts on the leftside of the relational expression represents a difference between theamount of data output from the buffer memory 26 during period Ts and theamount of data input to the buffer memory 26 during period Ts; and(Be−Bd)*Ts>Bd*Tw. (1−Bd/Be)*C is derived by moving (Be−Bd)Ts to the leftside of the expression. Since Bd<Be, 1−Bd/Be<1. Further, since Bd*Twinevitably becomes smaller than C, the amount of data corresponding toBd*Tw can be recorded into the container. At the time of jumping of thehead 17, a variation similar to that which has arisen in period CD shownin FIG. 17 arises in the amount of buffer. Further, during period Tsafter jumping of the head 17, a variation similar to that which hasarisen in period DE arises in the amount of buffer. A recording periodcomprises any of periods; namely, period Ts in which data are writteninto the disk 40, a period (<Tw) during which the head 17 jumps to arecording position on the disk 40, and a period (<Ts) during which thedata stored in the buffer memory 26 at the time of jumping of the headare written.

The disk 40 on which the AV data are recorded in the foregoing manner isimparted with a data format satisfying the relational expression(Be−Bd)*Ts>Bd*Tw.

At the time of reproduction, AV data are read from the disk 40 at thebit rate Be, and the thus-read AV data are written into the buffermemory 26. Simultaneously with writing of the AV data, the AV data aretransferred from the buffer memory 26 to the reproduction signalprocessing section 22 at the bit rate Bd (see FIG. 16). At this time, athreshold value such as that shown in FIG. 18 is determined beforehand.The threshold value corresponds to the amount of data stored in thebuffer memory 26 during period Ts [i.e., (Be−Bd)*Ts].

If the amount of data remaining in the buffer memory 26 is smaller thanthe threshold value, the AV data are output from the buffer memory 26 tothe reproduction signal processing section 22, and the AV data are readfrom the disk 40 at the bit rate Be. At points in time A, B, and D shownin FIG. 18, the amount of data remaining in the buffer memory 26 becomeslower than the threshold value, and hence the AV data are read at thebit rate Be. More specifically, In periods AB, BC, and DE shown in FIG.18, the amount of buffer is illustrated to drop after exhibiting anincrease. In reality, data are written into the buffer memory 26simultaneously with reading of data from the buffer memory 26, and afterlapse of time period Ts data are stored in the buffer memory 26 in anamount of (Be−Bd)*Ts.

In contrast, when the amount of data remaining in the buffer memory 26exceeds the threshold value, AV data are output from the buffer memory26 to the reproduction signal processing section 22, but reading of AVdata from the disk 40 is suspended. So long as the amount of dataexceeding (Be−Bd)*Ts remains in the buffer memory 26, even if the head17 jumps, the maximum amount of data transferred from the buffer memory26 becomes BdTw. Therefore, so long as the requirement (Be−Bd)*Ts>Bd*Twis satisfied, the amount of data required for reproduction will remainsufficient. Further, since reading of data is suspended, as mentionedabove, the amount of buffer memory 26 can be reduced the smallestpossible amount. At points in time C, E, and F, the amount of dataremaining in the buffer memory 26 exceeds the threshold value, and hencedata are output from only the buffer memory 26 during period between CD,period Ts between EF, and period Ts between FG. Period CD shown in FIG.18 represents jumping of the head 17 from one point of reproduction toanother point of reproduction. The maximum time required for jumpingaction in period CD corresponds to Tw. As shown in FIG. 18, areproducing period comprises any of the following periods; namely, aperiod Ts during which data are read from the disk 40, and a period(<Tw) during which the head 17 jumps to a reproduction position on thedisk 40.

As can be seen from FIG. 18, if jump time; that is, the time requiredfrom the time the head 17 is jumped to the time first actual data areacquired, is shorter than Tw, AV data are constantly reserved in anamount greater than (Be−Bd)*Ts in the buffer memory 26. Accordingly,reproduction data output from the buffer memory 26 during period Tw canbe ensured at all times. As has been described above, since jump timedoes not exceed Tw, data for reproduction will not run out.Specifically, as can be seen from FIG. 18, data are stored in an amountof (Be−Bd)*Ts is in the buffer memory 26 during period Ts. Since(Be−Bd)*Ts is greater than Bd*Tw, the amount of data is sufficient to beoutput during period Tw.

The maximum amount of data remaining in the buffer memory 26 is2*(Be−Bd)*Ts, and hence the buffer memory 26 must have a volume capableof storing such data. Given that the amount of remaining data at a breakbetween periods Ts or at the time of processing of data in units, eachunit having a predetermined amount, is (Be−Bd)*Ts, AV data are furtherread from the disk 40, with the result that the amount of remaining dataassumes the value 2*(Be−Bd)*Ts.

As mentioned above, seamless recording or reproduction of data amongarbitrary containers is ensured, and seamless virtual edition of data isalso ensured.

In a case where AV data are recorded or reproduced on a per-containerbasis, seamless recording or reproduction of data can be ensured. Inturn, units for editing must be limited to units of containers. In orderto enable editing of data from an arbitrary point, more detailed controlof the data recording/reproduction/editing system A may be achieved.

As shown in FIG. 19, a point table is provided in the header datapertaining to the title files. In this point table, there are writtendata pertaining to a start frame (reproduction start frame) and an endframe (reproduction end frame) with regard to each of points.

In the case of an m-th title file shown in FIG. 19, the containerdesignated by pointer 0 has start frame 4. The container designated bypointer 1 has start frame 2 and end frame 6. In a case where containerCn is reproduced according to address data pertaining to pointer 0, datalocated at the fourth frame of container Cn are reproduced. In a casewhere container Cn+2 is reproduced according to address data pertainingto pointer 1, data located between the second frame and the sixth frameof container Cn+2 are reproduced. In the flowchart shown in FIG. 7, thefourth frame of container Cn is specified as the editing start position;the final frame of the same is specified as the editing end position;the second frame of container Cn+2 is specified as the editing startposition; and the sixth frame of the same is specified as the editingend position.

In this case, since data are reproduced at the same timing as that ofthe AV data, frames other than edited frames of the container are notdisplayed during reproduction. For example, in the case of pointer 0 ofthe m-th title file shown in FIG. 19, AV data located in the firstthrough third frames are decoded but not displayed. AV data aredisplayed only after processing has progressed to the timing of thefourth frame. The point table is only for the purpose of controlling thetiming at which AV data are displayed. In this regard, although data areprocessed in a seamless manner, seamless display of AV data among linkedcontainers is not ensured.

As a result, the user can edit AV data through use of arbitrary frames,thus preventing unnecessary display of AV data or a failure to displaynecessary AV data.

Although in the previous embodiment the datarecording/reproduction/editing system A has been described to have thepoint table including frame data for each of points, time-stamp data orthe number of bytes following the head of a container may be used inplace of the point table.

Although the previous embodiment has described that AV data arerecorded, reproduced, and edited on a per-container basis and that theaddress data pertaining to containers, which are to be linked, arestored in the title file, the present invention is not limited to suchan embodiment and may employ another method.

The start and end positions of each of data blocks to be linked arestored sequentially. As shown in FIG. 20, data pertaining to the startand end positions of linked containers are sequentially stored in eachof the title files. As data pertaining to the start and end positions,address data pertaining to corresponding sectors, for example, arestored in the form of logical addresses. At the time of generation andcorrection of a title file during the recording, editing, deletion, andreproduction operations shown in FIGS. 6 through 11, data pertaining tothe start and end positions are stored in the title file. At this time,the link count table stores the number of times title files refer to anindividual sector. In this case, the sector acts as a unit recordingregion.

As mentioned above, in place of data pertaining to the start and endpositions of sectors, which are to be linked, these may be stored astart position and the amount of data which have been stored from thestart position. Even in this case, the link count table stores, for eachsector, the number of times title files refer to an individual sector.Even in these two cases, AV data are processed in the same manner as inthe case where data are processed on a per-container basis, except thatsectors, which are to be linked, are specified in a different way.

In a case where the start and end positions of linked sectors are storedin the title file or a case where the start position of a linked sectorand the amount of data which have been stored from the start positionare stored in the title file, the present invention has the advantage ofenabling editing of AV data at desired positions. In this case, however,seamless recording and reproduction of AV data is not ensured.Specifically, unlike the volume of a container, the unit volume of datato be continuously recorded is not specified, and hence the foregoingrelational expression cannot be satisfied, with the result that seamlessreproduction or recording of data is not ensured.

As mentioned above, in the data recording/reproduction/editing system Aaccording to the embodiment, a title file having link data storedtherein is prepared at the time of recording of AV data. When the AVdata are edited, the title file of the AV data is edited, and anothertitle file having another link data stored therein is stored. In otherwords, a portion of the title file can be shared among other titlefiles. In a case where a digest or a short version is produced from AVdata, there is no necessity for use of two VCRs, which would otherwisebe required in the case of a conventional datarecording/reproduction/editing system. Further, there is no necessityfor ensuring a storage area for use in recording a duplicate of AV data.As mentioned above, an original file and a virtual file are stored, thusenabling reproduction of AV data in various modes such as afull-reproduction mode, a digest mode, and a short version mode.

Although the embodiment of the present invention has been describedabove, the present invention is not limited to such an embodiment andmay be subjected to various modifications. For example, the previousembodiment has described the data pertaining to the management datatable being rewritten. However, the present invention is not limited tosuch an embodiment. Data pertaining to the management data table may berewritten every time a type of processing, such as recording, iscompleted. Alternatively, a new title file may be prepared every timerecording of AV data is started.

Further, the foregoing embodiment has described data of the managementdata table being recorded in the management region formed along theinnermost periphery of the disk 40. However, the present invention isnot limited to such an embodiment, and the data of the management datacan be recorded at an arbitrary position on the disk 40 and may berecorded in the user region; that is, a data region. According to thepresent invention, the amount of data stored in the management datatable can be changed on the basis of the number of title files or thenumber of pointers provided in the title file, which in turn makes itimpossible to define the size of the management region for storing themanagement data table. To prevent this, the management region sufficientfor storing the amount of data stored in the user region on the disk 40is ensured, and the data pertaining to the management data table arestored. In the event the management region becomes full or the amount ofdata remaining in the management region becomes smaller than apredetermined threshold value, an empty region in the user region isensured as a new management region. The size of the management region isset beforehand in consideration of a margin. Further, the datarecording/reproduction/editing system may be arranged such that, in theevent the volume of a new title file to be recorded exceeds the volumeof the management region, generation or recording of the new title filemay be disabled unless an existing title file is deleted.

Although the foregoing embodiment has been described by reference to acase where AV data are taken as principal data, the present invention isnot limited to such an example; the foregoing embodiment may also beapplied to solely video data or solely audio data.

INDUSTRIAL APPLICABILITY

As has been mentioned, in a data recording system and a data recordingmethod according to the present invention, when primary data arerecorded, a file (original file) is prepared. Another file (a virtualfile) is prepared through editing of the file. At least a portion of theprimary data can be accessed by a plurality of files. Editing of theprimary data, such as preparation of a digest of the primary data,becomes feasible, thereby eliminating a necessity for use of areproduction apparatus and a recording apparatus. The data recordingsystem manages only the plurality of files, which in turn eliminates anecessity for ensuring a region for use in recording a duplicate of theprimary data.

Further, in connection with the recording medium according to thepresent invention, data are reproduced according to the file (originalfile) prepared at the time of recording of primary data or according tothe file (virtual file) prepared by editing the file, thereby enablingreproduction of data in various modes, such as a full-reproduction modeor a digest reproduction mode. Further, the data are managed in the formof files, and hence the recording region on the recording medium can beeffectively utilized.

1. A data recording system for recording primary data, comprising: arecording section for recording primary data on a recording medium, inwhich primary data are recorded in each of a plurality of unit recordingregions of a predetermined length into which a recording area of therecording medium is divided; and a control section for generating anoriginal file when the recording section has recorded the primary dataon the recording medium, the original file storing link data formed as aresult of sequential arrangement of address data directly pertaining tothe unit recording regions in which the primary data have been recordedby the recording section, as well as for generating a virtual file bymeans of editing the original file in accordance with a user'sinstruction, the virtual file storing link data formed as a result ofsequential arrangement of address data directly pertaining to the unitrecording regions.
 2. The data recording system as defined in claim 1,wherein the control section prepares a virtual file by editing theoriginal file and/or the virtual file in accordance with a user'sinstruction.
 3. A data recording system for storing primary data on amedium, comprising: a recording section for recording primary data on arecording medium, in which primary data are recorded in each of aplurality of unit recording regions of a predetermined length into whicha recording area of the recording medium is divided; and a controlsection for generating a file at the time of recording of the primarydata, wherein the file stores, in the form of a logical address, linkdata which are formed by arranging in sequence address data directlypertaining to the unit recording regions in which the primary data havebeen recorded by the recording section, wherein the control sectiongenerates a new virtual file by means of editing the original file thatis prepared at the time of recording of the primary data in accordancewith a user's instruction and the control section generates a newvirtual file by means of editing an existing original file and/or anexisting virtual file in accordance with a user's instruction.
 4. Thedata recording system as defined in claim 1, wherein the virtual filecomprises at least a portion of address data pertaining to a file whichis used as a source for editing.
 5. The data recording system as definedin claim 1, wherein the control section prepares a new file on the basisof a plurality of files.
 6. The data recording system as defined inclaim 1, wherein when any of existing files is deleted, the controlsection deletes the file, and when a portion of any one of existingfiles is deleted, the control section deletes from the file one or aplurality of address data sets pertaining to the file.
 7. The datarecording system as defined in claim 1, wherein the control sectionprepares a link count table for managing the number of times files referto each of said unit recording regions, and the control section updatesdata pertaining to the prepared link count table or pertaining to a linkcount table read from the recording medium, through editing and/ordeletion of the files.
 8. The data recording system as defined in claim7, wherein a unit recording region assigned reference number 0 in thelink count table is handled as a recordable region; when the originalfile prepared at the time of recording of the primary data or a portionof the original file is deleted, the control section resets to zero thereference number assigned in the link count table to the correspondingunit recording regions to be deleted; and in contrast, when the virtualfile prepared by editing the existing file or a portion of the virtualfile is deleted, the control section decrements the reference numberassigned in the link count table to the corresponding unit recordingregions to be deleted.
 9. The data recording system as defined in claim8, wherein when a certain original file or a portion of the originalfile is deleted, another virtual file referring to the correspondingunit recording region to be deleted is corrected.
 10. The data recordingsystem as defined in claim 7, wherein the unit recording region assigned0 as a reference number in the link count table is handled as arecordable region, and when a certain file is wholly or partiallydeleted, the control section decrements the reference number assigned inthe link count table to the corresponding unit recording regions to bedeleted, regardless of whether the file to be deleted is an originalfile prepared at the time of recording of primary data or a virtual fileprepared by editing an existing file.
 11. The data recording system asdefined claim 1, wherein when overwriting of the entirety of a certainexisting file or overwriting of a portion of the file is instructed, thecontrol section prepares a new file with regard to the thus-overwrittenprimary data, and corrects the link data stored in the existing files ordeletes the existing files.
 12. The data recording system as defined inclaim 1, wherein the control section prepares a title set file forstoring the address data pertaining to the files and corrects the titleset file in response to preparation or deletion of the files.
 13. Thedata recording system as defined in claim 12, wherein the data recordingsystem writes into the recording medium, at predetermined timing, datapertaining to the generated, corrected, and deleted files, datapertaining to the link count table, and data pertaining to the title setfile.
 14. The data recording system as defined in claim 13, wherein thedata recording system reads from the recording medium data pertaining tothe files, the link count table, and the title set file, all of whichare written into the recording medium by the data recording system, andstores the thus-read data into a storage section of the data recordingsystem.
 15. The data recording system as defined in claim 1, wherein thedata recording system records primary data on and reproduces primarydata from each of said unit recording regions and data pertaining to areproduction start frame and a reproduction end frame of each unitrecording region are stored in the file.
 16. The data recording systemas defined in claim 1, wherein the data recording system records primarydata on and reproduces primary data from each of said unit recordingregions, and given that the minimum rate at which the data recordingsystem transfers data to the recording medium is Be, a bit rate at whichdata are reproduced is Bd, a time required from the time a head has madea maximum jump over the recording medium to the time first actual dataare acquired is Tw, and the amount of storage on the unit recordingregion of predetermined length is C, recording or reproduction of datais performed so as to satisfy the relational expressions(Be−Bd)*Ts>Bd*Tw, Ts=C/Be, and Be>Bd.
 17. The data recording system asdefined claim 3, wherein the control section prepares a new file on thebasis of a plurality of files.
 18. The data recording system as definedin claim 3, wherein when any of existing file is deleted, the controlsection deletes the file, and when a portion of any one of existingfiles is deleted, the control section deletes from the file one or aplurality of address data sets pertaining to the file.
 19. The datarecording system as defined in claim 3, wherein the control sectionprepares a link count table for managing the number of times files referto each of said unit recording regions, and the control section updatesdata pertaining to the prepared link count table or pertaining to a linkcount table read from the recording medium, through editing and/ordeletion of the files.
 20. The data recording system as defined in claim3, wherein when overwriting of the entirety of a certain existing fileor overwriting of a portion of the file is instructed, the controlsection prepares a new file with regard to the thus-overwritten primarydata, and corrects the link data stored in the existing files or deletesthe existing files.
 21. The data recording system as defined in claim 3,wherein the control section prepares a title set file for storing theaddress data pertaining to the files and corrects the title set file inresponse to preparation or deletion of the files.
 22. The data recordingsystem as defined in claim 3, wherein the data recording system recordsprimary data on and reproduces primary data from each of said unitrecording regions, and data pertaining to a reproduction start frame anda reproduction end frame of each unit recording region are stored in thefile.
 23. The data recording system as defined in claim 3, wherein thedata recording system records primary data on and reproduces primarydata from each of said unit recording regions, and given that theminimum rate at which the data recording system transfers data to therecording medium is Be, a bit rate at which data are reproduced is Bd, atime required from the time a head has made a maximum jump over therecording medium to the time first actual data are acquired is Tw, andthe amount of storage on the unit recording region of predeterminedlength is C, recording or reproduction of data is performed so as tosatisfy the relational expression (Be−Bd)*Ts>Bd*Tw, Ts=C/Be, and Be>Bd.24. The data recording system as defined in claim 19, wherein a unitrecording region assigned reference number 0 in the link count table ishandled as a recordable region; when the original file prepared at thetime of recording of the primary data or a portion of the original fileis deleted, the control section resets to zero the reference numberassigned in the link count table to the corresponding unit recordingregions to be deleted; and in contrast, when the virtual file preparedby editing the existing file or a portion of the virtual file isdeleted, the control section decrements the reference number assigned inthe link count table to the corresponding unit recording regions to bedeleted.
 25. The data recording system as defined in claim 19, whereinthe unit recording region assigned 0 as a reference number in the linkcount table is handled as a recordable region, and when a certain fileis wholly or partially deleted, the control section decrements thereference number assigned in the link count table to the correspondingunit recording regions to be deleted, regardless of whether the file tobe deleted is an original file prepared at the time of recording ofprimary data or a virtual file prepared by editing an existing file. 26.The data recording system as defined in claim 21, wherein the datarecording system writes into the recording medium, at predeterminedtiming, data pertaining to the generated, corrected, and deleted files,data pertaining to the link count table, and data pertaining to thetitle set file.
 27. The data recording system as defined in claim 1,wherein when a certain original file or a portion of the original fileis deleted, another virtual file referring to the corresponding unitrecording region to be deleted is corrected.
 28. The data recordingsystem as defined in claim 26, wherein the data recording system readsfrom the recording medium data pertaining to the files, the link counttable, and the title set file, all of which are written into therecording medium by the data recording system, and stores the thus-readdata into a storage section of the data recording system.
 29. The datarecording system as defined in claim 1, wherein the address datapertaining to the primary data are arranged in sequence of reproductionof the corresponding unit recording regions of the primary data.
 30. Thedata recording system as defined in claim 1, wherein the predeterminedlength of each of the unit recording regions comprises a number of bitscorresponding to an amount of data whose recording and reproductionrequires a few seconds.
 31. A data recording and reproducing system forrecording and reproducing primary data on a rewritable recording medium,comprising: a head to write and to read out the primary data on therecording medium; a recording section for recording the primary data onthe recording medium, the recording section making the head to jump to aregion to which the primary data is written; and a reproducing sectionfor reproducing the primary data on the recording medium, thereproducing section making the head to jump to a region from which theprimary data is read out, wherein the recording section and thereproducing section respectively record and reproduce the primary datain unit recording regions, into which a recording area of the recordingmedium is divided, according to the formulas:(Be−Bd)Ts>BdTw,Ts=C/Be, andBe>Bd, wherein Be is minimum data transmission rate to the recordingmedium, Bd is reproduction bit rate of the primary data, Tw is timeinterval from timing when the head starts jumping a longest distance onthe recording medium to timing when a first reproduction data of theprimary data is obtained after the jumping and C is a capacity of theunit recording region.
 32. A reproducing system for reproducing primarydata on a recording medium, comprising: a head to read out the primarydata on the recording medium; a reproducing section for reproducing theprimary data on the recording medium, the reproducing section making thehead to jump to a region from which the primary data is read out,wherein the primary data are recorded in unit recording regions, intowhich a recording area of the recording medium is divided, thereproducing section reproduce primary data according to followingformulas:(Be−Bd)Ts>BdTw,Ts=C/Be, andBe>Bd, wherein Be is minimum data transmission rate to the recordingmedium, Bd is reproduction bit rate of the primary data, Tw is timeinterval from timing when the head starts jumping a longest distance onthe recording medium to timing when a first reproduction data of theprimary data is obtained after the jumping and C is a capacity of theunit recording region.
 33. A method of recording and reproducing primarydata on a rewritable recording medium, comprising: recording andreproducing the primary data in unit recording regions, into which arecording area of the recording medium is divided, wherein the recordingand the reproducing of the primary data respectively are carried outaccording to following formulas:(Be−Bd)Ts>BdTw,Ts=C/Be, andBe>Bd, wherein Be is minimum data transmission rate to the recordingmedium, Bd is reproduction bit rate of the primary data, Tw is timeinterval from timing when a longest jump of reproduction position on therecording medium starts to timing when a first reproduction data of theprimary data is obtained after the jump and C is the capacity of theunit recording region.
 34. A data recording system for recording primarydata on a recording medium, comprising: a recording section forrecording primary data on the recording medium, in which primary dataare recorded in each of a plurality of unit recording regions; and acontrol section for generating an original file when the recordingsection has recorded the primary data on the recording medium, theoriginal file storing link data formed as a result of sequentialarrangement of address data pertaining to the unit recording regions inwhich the primary data have been recorded by the recording section, aswell as for generating a virtual file by means of editing the originalfile in accordance with a user's instruction, the virtual file storinglink data formed as a result of sequential arrangement of address datapertaining to the unit recording regions; wherein the virtual filestores time-stamp data indicating reproduction start timing andreproduction end timing of the primary data in each unit recordingregions linked by the link data of the virtual file.
 35. A datarecording method for recording primary data on a recording medium,comprising the steps of: generating an original file when primary dataare recorded in each of a plurality of unit recording regions on therecording medium, the original file storing link data formed as a resultof sequential arrangement of address data pertaining to the unitrecording regions in which the primary data have been recorded;generating a virtual file by means of editing the original file inaccordance with a user's instruction, the virtual file storing link dataformed as a result of sequential arrangement of address data pertainingto the unit recording regions; and storing time-stamp data in thevirtual file, the time stamp data indicating reproduction start timingand reproduction end timing of the primary data in each unit recordingregions linked by the link data of the virtual file.